System for data card emulation

ABSTRACT

An improved system for data card emulation involves a phone that can emulate any one of multiple data cards corresponding to multiple entities. The phone includes a memory for storing bar code information corresponding to data cards of the multiple entities. It provides an interface for identifying an entity and a display for displaying a bar code corresponding to a data card of the entity. The interface may include at least one of a bar code reader or a bar code emulator. The interface may include at least one of a magnetic stripe reader or a magnetic stripe emulator. The interface may be a transceiver such as a pulsed light transceiver.

CROSS-REFERENCE TO RELATED APPLICATIONS

This Non-provisional application is a continuation of U.S.Non-provisional application Ser. No. 13/431,289, filed Mar. 27, 2012,now U.S. Pat. No. 8,622,300, issued Jan. 7, 2014, which is acontinuation of U.S. Non-provisional application Ser. No. 12/380,058,filed Feb. 23, 2009, now U.S. Pat. No. 8,141,780, issued Mar. 27, 2012,which claims the benefit of U.S. Provisional Application Ser. No.61/066,832, filed Feb. 23, 2008 by Lawson et al., titled “System andMethod for Data Card Emulation”, which is incorporated by referenceherein in its entirety.

FIELD OF THE INVENTION

The present invention relates generally to a system for data cardemulation. More particularly, the present invention relates to the useof an interface to identify an entity such that a phone can emulatemultiple data cards having different bar codes corresponding todifferent entities.

BACKGROUND OF THE INVENTION

It is quite common for a person to currently have to carry manydifferent types of data cards in their wallet or purse. Such data cardsinclude credit cards, debit cards, loyalty cards, identification cards,and the like. Keeping track of such cards and being able to quicklylocate such cards can be quite cumbersome. Therefore, there is a needfor an improved system and method for a single card to function asmultiple data cards.

SUMMARY OF THE INVENTION

The present invention is an improved system for data card emulation. Asingle data card is able to emulate, or function as, any one of manydifferent types of cards that a person might otherwise have to carry ina wallet or purse. This improved system for data card emulation, oftenreferred to herein as CardCard, includes an improved system forconveying data that enables the card to both read and write information.As such, various types of card information such as barcode and/ormagnetic stripe information for multiple data cards can be read into theCardCard, stored in a memory, and then later used (in write mode) toemulate a given data card. The CardCard can also operate in atransceiver mode whereby it can communicate with another CardCard (alsooperating in a transceiver mode) or with some other comparabletransceiver device. Various techniques are provided for identifyingwhich entity's data card to emulate. Under one arrangement, the CardCardcommunicate with another device to determine which entity's card toemulate. Under another arrangement, an interface on the card is used toselect an entity to emulate. A CardCard data management system isprovided to manage the data residing in a CardCard's memory. In anotherembodiment, the improved system for conveying data is integrated into acellphone, a smart card, a personal digital assistant (PDA), a watch, akeychain, a kiosk, or other object enabling that object to read andwrite information as if it were a CardCard.

The improved system for conveying data of the invention includes a firstlight conduit having a first opening at a first end, a second opening ata second end, and a side opening. It also includes a first light sourcethat outputs a first light that initially enters the first light conduitthrough the side opening, reflects off the first light conduit, andexits the first opening. It also includes a first detector that detectsa second light and a first processor interfaced with the first detector,where the first processor conveys data based on at least one of thefirst light or the second light.

Under one arrangement, after exiting the first opening the first lightencounters a barcode having black lines and white lines. The first lightis absorbed by the black lines and reflected by the white lines therebyproducing the second light such that the data conveyed by the secondlight corresponds to barcode information in accordance with the barcode.The barcode can be passed by the first opening or the first opening canbe passed by the barcode. The barcode can be on a data card or onanother object. The barcode can distinguish one of a plurality ofentities associated with a data card.

The first light source can be a light emitting diode (LED) or can be anambient light source.

The system can be integrated into one of a data card, a cellular phone,a smart phone, a PDA, a watch, a keychain, a kiosk, a point-of-saledevice, a data management device, a portable object, or a fixed object.It may also include at least one of a first memory, a first battery, afirst switch, a first light waveguide, a first status indicator, or afirst display.

Under one arrangement, the second light enters the first light conduitthrough the first opening and exits the second opening. Under anotherarrangement, the second light reflects off the first light conduit afterentering the first opening and before exiting the second opening.

The first light source can be interfaced with the first processor andcan output the first light in accordance with a barcode pattern. Underone arrangement, the first light source and the first detector canfunction as a first transmitter and a first receiver of a first pulsedlight transceiver. The first pulsed light transceiver can useOn-Off-Keying (OOK).

The improved system for conveying data can include a second light sourcethat outputs the second light that initially enters the first lightconduit through the first opening and exits the second opening. Theimproved system can also include a second detector for detecting thefirst light having exited the first opening and a second processorinterfaced with the second light source and the second detector thatconveys data based on at least one of the first light or the secondlight.

The improved system for conveying data can also include a second lightconduit where the first light reflects through the first light conduitand then reflects through the second conduit prior to being detected bythe second detector and the second light reflects through the secondlight conduit and then reflects through the first conduit prior to beingdetected by the first detector.

Under one arrangement, the second light source outputs the second lightthrough a side opening in the second light conduit.

The improved system for conveying data can also include at least one ofa second memory, a second battery, a second switch, a second lightwaveguide, a second status indicator, or a second display.

The improved system for conveying data can also include at least one ofa magnetic stripe detector or a magnetic stripe emulator.

BRIEF DESCRIPTION OF THE DRAWINGS

The present invention is described with reference to the accompanyingdrawings. In the drawings, like reference numbers indicate identical orfunctionally similar elements. Additionally, the left-most digit(s) of areference number identifies the drawing in which the reference numberfirst appears.

FIG. 1 illustrates the basic concept of the present invention where onedata card referred to herein as CardCard is able to emulate any one of aplurality of data cards;

FIG. 2 depicts an exemplary method of the present invention;

FIG. 3 depicts various devices that can be used to obtain barcode and/ormagnetic stripe information from a data card;

FIG. 4 a depicts an exemplary kiosk that can be used to manage data onthe CardCard;

FIG. 4 b depicts an exemplary CardCard data management device inaccordance with one embodiment of the present invention;

FIG. 5 a depicts an exemplary bar code reader in accordance with anotherembodiment of the present invention;

FIG. 5 b depicts an alternative bar code reader in accordance with stillanother embodiment of the present invention;

FIG. 5 c depicts a barcode reader/emulator—light transceiver operatingas an OOK pulsed light transceiver with a second detector and secondlight source functioning as a second OOK pulse light transceiver;

FIG. 5 d depicts a first barcode reader/emulator—light transceiver and asecond barcode reader/emulator—light transceiver operating in the lighttransceiver mode;

FIG. 6 a depicts a first exemplary CardCard circuitry in accordance withone embodiment of the present invention;

FIG. 6 b depicts a second exemplary CardCard circuitry in accordancewith another embodiment of the present invention;

FIG. 6 c depicts a third exemplary CardCard circuitry in accordance withyet another embodiment of the present invention;

FIG. 6 d depicts a fourth exemplary CardCard circuitry in accordancewith yet another embodiment of the present invention;

FIG. 6 e depicts a fifth exemplary CardCard circuitry in accordance witha further embodiment of the present invention;

FIG. 6 f depicts a sixth exemplary CardCard circuitry in accordance witha still further embodiment of the present invention;

FIG. 7 depicts another view of the exemplary CardCard data managementdevice previously depicted in FIG. 4 b;

FIG. 8 depicts an exemplary CardCard Data Management System;

FIG. 9 depicts an exemplary CardCard Website;

FIG. 10 a depicts an exemplary magnetic stripe;

FIG. 10 b depicts an exemplary barcode;

FIG. 10 c depicts a top down view of an exemplary entity identifyingdevice having a magnetic stripe along one side of a slot;

FIG. 10 d depicts a top down view of an exemplary entity identifyingdevice having a barcode along the bottom of a slot;

FIG. 10 e depicts a top down view of an exemplary entity identifyingdevice having a magnetic stripe along one side of a slot and a barcodealong the bottom of the slot;

FIG. 10 f depicts a first three dimensional view of an exemplary entityidentifying device;

FIG. 10 g depicts a second three dimensional view of an exemplary entityidentifying device;

FIG. 11 depicts an exemplary usage of a CardCard at an entitypoint-of-sale;

FIG. 12 depicts an exemplary method corresponding to usage of a CardCardat an entity point-of-sale;

FIG. 13 a depicts an exemplary CardCard display;

FIG. 13 b depicts another exemplary CardCard display; and

FIG. 14 depicts examples of various types of devices that could employCardCard circuitry to enable them to provide CardCard functionality.

DETAILED DESCRIPTION OF THE INVENTION

The present invention will now be described more fully in detail withreference to the accompanying drawings, in which the preferredembodiments of the invention are shown. This invention should not,however, be construed as limited to the embodiments set forth herein;rather, they are provided so that this disclosure will be thorough andcomplete and will fully convey the scope of the invention to thoseskilled in the art. Like numbers refer to like elements throughout.

The present invention provides a system and method for data cardemulation. Specifically, the present invention involves a data cardreferred to herein as CardCard that is able to emulate any one of aplurality of data cards. The CardCard will work with existing data cardinfrastructure in the same manner as if a user used a different one ofthe plurality of data cards at respective entities (e.g., businesses).

FIG. 1 illustrates the basic concept of the present invention where onedata card is able to emulate any one of a plurality of data cards.Referring to FIG. 1, a plurality of data cards 100, for example,includes various types of loyalty cards. The plurality of data cards 100could alternatively or additionally include various types of transactioncards such as credit cards or debit cards, and generally could includeany kind of data card having a barcode and/or magnetic stripe. Barcodeinformation and/or magnetic stripe information 102 is stored on aCardCard 104 such that the CardCard 104 can emulate any one of theplurality of data cards 100 by emulating the barcode and/or magneticstripe information normally conveyed by the card.

FIG. 2 depicts an exemplary method of the present invention. Referringto FIG. 2, the method 200 comprises a first step 202 which is to obtainmagnetic stripe and/or barcode information of a plurality of data cardscorresponding to a plurality of entities. The magnetic stripe and/orbarcode information is stored on a portable conveyance device in asecond step 204. The portable conveyance device may, for example,resemble a typical data card. In a third step 206, an entity isdistinguished corresponding to one of the plurality of cards for whichthe magnetic stripe and/or barcode information is required. In a fourthstep 208, the portable conveyance device conveys to the entity themagnetic stripe and/or barcode emulation corresponding to the entity'sdata card.

In accordance with the invention, the magnetic stripe and/or barcodeinformation of a plurality of data cards corresponding to a plurality ofentities can be obtained in one or more of several ways includingreading such information directly from individual data cards orreceiving a data file or other data stream that includes suchinformation corresponding to one or more data cards. Once obtained, suchinformation can be stored (or otherwise described) in a memory for lateruse. An entity can be distinguished using various approaches includingusing a user interface of the portable conveyance device or a userinterface of a computing device associated with the portable conveyancedevice to select the entity. Alternatively, a radio frequencytransmission or other form of transmission could be received by theportable conveyance device or a computing device associated with theportable conveyance device, or a barcode, magnetic stripe, or otherrecognizable information associated with the entity could be recognized(or read) by the portable conveyance device or by a computing deviceassociated with the portable conveyance device. Similarly, magneticstripe and/or barcode information corresponding to the distinguishedentity can be conveyed via a writeable magnetic stripe and/or a display,via an emulation approach whereby existing infrastructure reads theinformation as if reading the actual entity data card, or via atransmission from the portable conveyance device to a device associatedwith the entity that is capable of receiving the transmission, whichwould convey the magnetic stripe and/or barcode informationcorresponding to the entity (and the user of the portable conveyancedevice). Under one approach, a device associated with the entity wouldcommunicate with the portable conveyance device as required to searchthe memory of the portable conveyance device to locate and retrieve themagnetic stripe and/or barcode information that it would recognize ascorresponding to one of its data cards.

FIG. 3 depicts various devices that can be used to obtain barcode and/ormagnetic stripe information from a data card. Referring to FIG. 3, acomputer system 300 includes a computer 302, a display 304, and akeyboard 306 that can be used to receive and store information obtainedfrom such devices. The computer system 300 may be located, for example,in a home or business. Various examples of barcode readers (or scanners)308 a-308 d are depicted including a slot reader 308 a, a handheldreader 308 b, a horizontal scanner 308 c, and a pen type barcode reader308 d. Also shown is a computer printer 310 having scanningcapabilities. FIG. 3 also depicts a magnetic stripe reader 312 and acombination barcode/magnetic stripe reader 314. In accordance with thepresent invention, any of a variety of reader/scanner devices can beused to obtain barcode and/or magnetic stripe information that can becommunicated via a wire or wirelessly to a computer system where it canbe managed as desired. Such barcode and/or magnetic stripe informationcan also be transferred to or from the computer system 300 over anetwork, for example, the Internet.

FIG. 4 a depicts an exemplary kiosk 402 that can be used to manage thedata stored on the CardCard. In accordance with the present invention, aCardCard user would place his or her CardCard 104 into a slot 404 in thekiosk 402. The kiosk 402 provides an interface for the user to add,delete, or modify information pertaining to a data card of one or moreentities (e.g., a vendor, a school, etc). For example, a kiosk might beused in a mall to allow shoppers to populate their CardCard with thedata card information of one or more of the stores in the mall at whichthe shopper likes to shop. Such data card information would typicallyinclude an identifier (e.g., name) for the entity, barcode informationand/or magnetic stripe information, and possibly a logo.

FIG. 4 b depicts an exemplary CardCard data management device inaccordance with one embodiment of the present invention. Referring toFIG. 4 b, a computer system 300 includes a computer 302 that has a dataport 406, for example a Universal Serial Bus (USB) port, to which aCardCard data management device 408 is connected via a cable, forexample, a USB cable 409. Optionally, a CardCard data management device408 may be connected wirelessly to a computer 302. The CardCard datamanagement device 408 includes a slot 410 in which a CardCard 104 isinserted. Thereafter, the CardCard data management device 408 interfaceswith the CardCard 104 as required to manage information maintained onthe CardCard 104 to include adding a vendor's data card information tothe CardCard 104 at a Point-of-sale (POS). Under one arrangement, one ormore barcode and/or magnetic stripe reader/scanner devices like orsimilar to those described in relation to FIG. 3 are associated with oneor more other data ports 412 of the computer 302. Under anotherarrangement, such reader/scanner devices are associated with one or moreother data ports 414 of the CardCard data management device 408.

The invention includes several embodiments of an improved system forconveying data that enable a CardCard to read and write barcode and/ormagnetic stripe information and to function as a transceiver. Dependingon the embodiment, this improved system for conveying data is alsoreferred to herein as a barcode reader, barcode emulator, barcodereader/emulator, light transceiver, magnetic stripe detector, magneticstrip emulator, or a magnetic field transceiver.

FIG. 5 a depicts an exemplary barcode reader in accordance with anotherembodiment of the present invention. Referring to FIG. 5 a, a barcodereader 500 includes a light conduit 502 having a first opening 504 atone end, a second opening 506 at the other end, and a side opening 508.Light from a light source 510, for example a light emitting diode (LED),enters the side opening 508 and reflects through the light conduit 502where it then reflects off a barcode. 512 of a data card being passed bythe first opening 504. The light then reflects through the light conduit502 and exits the second opening 506 where it is detected by a detector514. Alternatively, the first opening 504 of a barcode reader 500 can bemoved relative to a stationary barcode 512. As such, when reading abarcode, a barcode reader 500 requires the same relative movement asdoes a pen type barcode reader 308 d. Light from a light source 510 isabsorbed by the black lines and reflected by the white lines of barcode512. The detector therefore detects the presence or absence of lightover time, which corresponds to the barcode sequence. Under onearrangement, the light conduit 502 is substantially flat allowing it tobe configured within a data card. Under another arrangement, the lightconduit 502 is substantially round, for example an optical fiber.

FIG. 5 b depicts an alternative bar code reader in accordance with stillanother embodiment of the present invention. Referring to FIG. 5 b, abarcode reader 516 is the same as the barcode reader 500 of FIG. 5 aexcept the light source is ambient light 518.

The exemplary bar code reader 500 of FIG. 5 a can also be configured asa bar code emulator and/or as pulsed light transceiver. Essentially, abarcode reader/emulator—light transceiver 520 can be operated in one ofthree modes depending on what it interfaces with at the first opening504 of light conduit 502. As depicted in FIG. 5 a, a first mode of thebarcode reader/emulator—light transceiver 520 is to read a barcode viathe first opening 504. In a second mode, the barcodereader/emulator—light transceiver 520 outputs pulsed light from a lightsource 510 in accordance with a barcode pattern so as to emulate abarcode to another barcode reader, a CardCard barcode reader 500 or 516,or another barcode reader/emulator—light transceiver 520. In a thirdmode, the light source 510 and the detector 514 function as atransmitter and a receiver of a On-Off-Keying (OOK) pulsed lighttransceiver, respectively. FIG. 5 c depicts a barcodereader/emulator—light transceiver 520 operating as an OOK pulsed lighttransceiver with a second detector 522 and second light source 524functioning as a second OOK pulse light transceiver, which might beimplemented in the kiosk 402 of FIG. 4 a, the CardCard data managementdevice 408 of FIG. 4 b, or another device.

FIG. 5 d depicts a first barcode reader/emulator—light transceiver 520and a second barcode reader/emulator—light transceiver 520 operating inthe third (light transceiver) mode. The dashed arrows, if shown alone,could indicate the leftmost barcode reader/emulator—light transceiver520 operating in the second (barcode emulator) mode and the rightmostbarcode reader/emulator—light transceiver 520 operating in the first(barcode reader) mode. Similarly, the solid arrows, if shown alone,could indicate the rightmost barcode reader/emulator—light transceiver520 operating in the first (barcode emulator) mode and the leftmostbarcode reader/emulator—light transceiver 520 operating in the second(barcode reader) mode.

FIG. 6 a depicts a first exemplary CardCard circuitry 600 in accordancewith one embodiment of the present invention. Referring to FIG. 6 a, thefirst CardCard circuitry 600 includes a processor 602 that interfaceswith a barcode reader/emulator—light transceiver 520, a memory 604, abattery 606, a first pressure switch 608, a second pressure switch 610,and a light waveguide 612. The processor 602 may also interface with oneor more status indicators (not shown) to include one or more additionalLEDs. The processor 602 may also interface with a display such as atouch screen, which might be used, for example, to display an entityicon, status information, or other entity information, and/or to providean interface for selecting an entity or otherwise managing thefunctionality of the CardCard 104. Use of a display is discussed belowin relation to FIGS. 13 a and 13 b.

Referring again to FIG. 6 a, the pressure switch 608 is used, forexample, to activate the barcode reader/emulator modes of the CardCardand the pressure switch 610 is, for example, used to activate the lighttransceiver mode of the CardCard. The light waveguide 612 enables anyform of barcode reader to read the barcode emulator mode output of abarcode reader/emulator—light transceiver 520. Specifically, for thebarcode emulator mode output to be read by a slot reader 308 a, theCardCard only has to be placed into the slot reader 308 a (i.e., itdoesn't have to slide). A handheld reader 308 b and a horizontal scanner308 c can read the output at any angle other than exactly parallel tothe light waveguide 612, and a pen type barcode reader 308 d can readthe output by pointing the pen type barcode reader 308 d at any locationof the light waveguide 612, where the pen type barcode reader 308 d doesnot move while reading the output. The light waveguide 612 also allowstwo (or more) CardCards to convey information using their respectivebarcode reader/emulator—light transceivers 520 by merely placing theirrespective light waveguides 612 close enough together such that lightcan traverse between them.

Under one arrangement, the light from the light source 510 is visible tothe user of the CardCard thereby providing an indication of status. Forexample, after the first pressure switch 608 is activated by a userholding the top of the CardCard, the light source 510 would stay oncontinuously during the barcode reader mode as required to read thebarcode of an entity, which might be located, for example, at a cashregister. After successfully reading the barcode, the same light source510 would begin operating in barcode emulator mode where it wouldrapidly flash on and off in accordance with the appropriate barcode fordata card of the recognized entity. This flashing on and off wouldindicate the card was ready to insert into a barcode reader.Alternatively, the same light source 510 might flash on and off with aspecific pattern to indicate whether the card was able to successfullyrecognize the barcode of the entity. Under another arrangement one ormore other LEDs are used to indicate a mode of the card and/or statusinformation.

FIG. 6 b depicts a second exemplary CardCard circuitry 612 in accordancewith another embodiment of the present invention. Referring to FIG. 6 b,the second exemplary CardCard circuitry 614 is the same as the firstexemplary CardCard circuitry 600 except it also includes circuitrycorresponding to a magnetic stripe detector 616 and a magnetic stripeemulator 618. As such, the magnetic stripe detector 616 can be used inconjunction with the barcode reading mode of barcodereader/emulator—light transceiver 520 to obtain the magnetic stripe andbarcode information related to a data card, or can be used to identifyan entity, where an entity's magnetic stripe information may be read,for example, near a cash register. The magnetic stripe emulator 618 canalso be used in conjunction with the barcode emulation mode of barcodereader/emulator—light transceiver 520 to convey the magnetic stripe andbarcode information to corresponding reader devices, where the magneticstripe emulator 618 generates a varying magnetic field corresponding tothe information typically encoded on a magnetic stripe. A magneticstripe detector 616 and a magnetic stripe emulator are described in U.S.Pat. No. 4,701,601, which is incorporated herein by reference.Alternative magnetic stripe detector/emulator approaches are describedin U.S. Pat. No. 6,811,082, which is also incorporated herein byreference.

The combination of the magnetic strip detector 616 and the magneticstrip emulator 618 provides for three modes of operation similar to thethree operational modes of the barcode reader/emulator—light transceiver520. Specifically, the first mode is the magnetic stripe detector mode,the second mode is the magnetic stripe emulator mode, and the third modeis the magnetic field transceiver mode where data would be conveyed inaccordance with a defined modulation scheme for modulating a magneticfield. As such, when the magnetic strip detector 616 and the magneticstrip emulator are operating in magnetic field transceiver mode with asecond magnetic stripe detector and second magnetic stripe emulator thenany form of data can be conveyed including information (or data)representing a barcode, an entity name, a logo, etc. A magnetic fieldtransceiver is described in U.S. Pat. No. 3,551,795 incorporated hereinby reference.

FIG. 6 c depicts a third exemplary CardCard circuitry 618 in accordancewith yet another embodiment of the present invention. Referring to FIG.6 c, the third exemplary CardCard circuitry 620 is the same as thesecond exemplary CardCard circuitry 614 except it does not includecircuitry corresponding to the barcode reader/emulator—light transceiver520. As such, the magnetic stripe detector 616 can be used to obtainmagnetic stripe information related to a data card and the magneticstripe emulator 618 can be used to convey magnetic stripe information toa corresponding magnetic stripe reader device.

FIG. 6 d depicts a fourth exemplary CardCard circuitry 622 in accordancewith still another embodiment of the present invention. Referring toFIG. 6 d, the fourth exemplary CardCard circuitry 622 is the same as thesecond exemplary CardCard circuitry 614 except it does, not include amagnetic stripe decoder 616. As such, any magnetic stripe informationthe CardCard obtains for use by the magnetic stripe emulator 618 toemulate a magnetic stripe must be received via barcodereader/emulator—light transceiver 520 operating in light transceivermode.

FIG. 6 e depicts a fifth exemplary CardCard circuitry 624 in accordancewith a further embodiment of the present invention. Referring to FIG. 6e, the fifth exemplary CardCard circuitry 624 is the same as the secondexemplary CardCard circuitry 614 except it does not include a barcodereader/emulator—light transceiver 520. In place of the barcodereader/emulator—light transceiver 520 is a barcode emulator 626comprising a light conduit 502 and a light source 510 used to producebarcode emulator output through opening 504 to light waveguide 612. Assuch, any barcode information the CardCard obtains for use by barcodeemulator 626 to emulate a barcode must be received via magnetic stripedetector 616 when operating in magnetic field transceiver mode withmagnetic stripe emulator 618.

FIG. 6 f depicts a sixth exemplary CardCard circuitry 628 in accordancewith a still further embodiment of the present invention. Referring toFIG. 6 f, the sixth exemplary CardCard circuitry 628 is the same as thefifth exemplary CardCard circuitry 624 except it does not include amagnetic stripe detector 616 and it does include electrical contacts 630used to provide a wired communications link to the processor 602. Assuch, any magnetic stripe or barcode information the CardCard obtainsfor use by the magnetic stripe emulator 618 to emulate a magnetic stripeor by the barcode emulator 626 to emulate a barcode must be received viaelectrical contacts 630.

In reference to the six exemplary CardCard circuitries 600, 614, 620,622, 624, and 628 one skilled in the art will recognize that thelocations of the various components can be varied, the number and typeof switches can vary, and other changes can be made to the circuitrywithin the scope of the current invention such as extending the lightwaveguide 612 around one or more sides of the card. Furthermore, for thefirst five exemplary circuitries 600, 614, 620, 622, and 624, electricalcontacts 630 like those in the sixth exemplary circuitry 628 could alsobe used to provide an interface to the processor 602 to enable anelectrical circuit for wired communications between the CardCard 104 anda kiosk 402, a CardCard data management device 408, or some otherdevice. Generally, various designs of the CardCard may be employed inaccordance with the invention to achieve a desired a size, thickness,and/or flexibility, for example, the size, thickness, and flexibility ofa typical credit card. Under one arrangement, the CardCard circuitry canbe implemented using flexible circuit board technology. Alternatively,the CardCard circuitry can be implemented using rigid-flex circuit boardtechnology or using rigid circuit board technology.

FIG. 7 depicts another view of the exemplary CardCard data managementdevice 408 previously depicted in FIG. 4 b that is configured tointerface with the second exemplary CardCard circuitry 614. One skilledin the art will recognize that a CardCard data management device 408 canbe configured to interface with any one or more of the six exemplaryCardCard circuitries. One skilled in the art will also recognize thatthe basic circuitry used to interface with any one or more of the sixexemplary CardCard circuitries can be employed in a kiosk 402 or someother device such as one tailored for an entity POS. Referring to FIG.7, the CardCard data management device 408 has a USB cable 409 forconnecting to a computer 302 and an additional USB port 414 forconnecting to a barcode and/or magnetic stripe reading device such asthose described in relation to FIG. 3. A CardCard 104 is inserted intothe slot 410 of the CardCard data management device 408. The barcodereader/emulator—light transceiver 520 of the CardCard 104 is therebyaligned with a second detector 522 and a second light source 524included in the CardCard data management device 408. Similarly, themagnetic stripe reader 616 and the magnetic stripe emulator 618 of theCardCard 104 are thereby aligned with second magnetic stripe emulator704 and second magnetic stripe reader 706 of the CardCard datamanagement device 408, respectively. Thereafter, CardCard datamanagement device 408 can convey barcode and/or magnetic stripeinformation to and from CardCard 104 using any of several modes ofcommunication. Specifically, CardCard data management device 408 caninterface with the barcode reader/emulator—light transceiver 520 of theCardCard 104 using any of its three modes of operation (i.e., barcodereader mode, barcode emulator mode, or light transceiver mode). Usingthe light transceiver mode, information other than barcode informationcan be conveyed and other types of functions can be performed.Similarly, CardCard data management device 408 can interface with themagnetic stripe reader 616 and the magnetic stripe emulator 618 usingany of their three modes of operation (i.e., magnetic stripe detectormode, magnetic stripe emulator mode, or magnetic field, transceivermode). Using the magnetic field transceiver mode, information other thanmagnetic stripe information can be conveyed and other types of functionscan be performed. Furthermore, information other than barcode, andmagnetic stripe information can be conveyed and other types of functionscan be performed using electrical contacts 630 (not shown).

Referring again to FIG. 7, the first and second activation buttons 700and 702 are aligned with the first and second pressure switches 608 and610, respectively, such that, when the first activation button 700 ispressed, pressure is applied to the first pressure switch 608 and, whenthe second activation button 702 is pressed, pressure is applied to thesecond pressure switch 610. As such, only the first activation button700 can be pressed, only the second activation button 702 can bepressed, or the first activation button 700 and the second activationbutton 702 can be both pressed at the same time to control threeactivation states of the CardCard data management device 408. Control ofthe CardCard data management device 408 can also be provided via thecomputer 302 via USB cable 409.

The ability of the CardCard data management device 408 to interface witha computer system 300, to interface with a barcode and/or magneticstripe reader device (connected to computer 302 data port 412 or to datamanagement device 408 data port 414), and to interface with a CardCard104 enables it to be used to populate information from multiple entitydata cards onto a CardCard. Such interfaces enable it to be used by anentity to add its own information to a customer's card and alternativelyenable a device to scan the memory of a customer's CardCard in order tofind the barcode and/or magnetic stripe information for the data cardcorresponding to that entity. Furthermore, the CardCard data managementdevice enables the CardCard to be used as a smart card whereby varioustypes of information corresponding to customer transactions could bestored on the CardCard, such as account balances and the like. When usedas a smart card, various well known security features would likely needto be employed such as data encryption and user authenticationtechniques such as requiring a PIN and/or employing biometricauthentication techniques, for example, requiring a thumb print match.One or more of such security features can also be used when a CardCardis not being used as a smart card.

FIG. 8 depicts an exemplary CardCard Data Management System that couldbe executed on a computing system 300. Referring to FIG. 8, a display304 provides a menu driven user interface for performing various actionsrelated to information related to the CardCard 104 that is maintained ina local database maintained on a hard drive of the computer 302 of thecomputing system 300 and in a database maintained in the memory 604 ofthe CardCard 104. Ten functions are listed on the menu, but one skilledin the art will recognize that different functions, a differentinterface, or any of many different programs (or applications) can beused to manage CardCard data in accordance with the present invention.As shown, function #1 allows a user to manage information stored in alocal database pertaining to entities offering data cards. Typically, auser would use function #1 to add, delete, or edit entity records.Similarly, function #2 allows a user to manage information stored in thememory of the CardCard corresponding to the entities for which theCardCard has respective data card information. Function #3 would be usedto make changes to either database as appropriate to keep it currentwith changes made to the other database. Function #4 would automaticallylog on to a CardCard website (as described below) where informationpertaining to entities, particularly vendors, would be available.Function #5 would log on to an entity website, perhaps to downloadentity data card information or to support a transaction. The entity maybe identified via the computer 302 or may be selected via the CardCard.Function #6 would enable a CardCard to be erased of any or allinformation stored in the CardCard's memory. Function #7 would copyinformation contained in the memory of a CardCard into the memory of adifferent CardCard. Function #8 would allow the production of any one ofseveral different types of reports concerning the local and/or CardCarddatabases or, for example, could list entity websites for which datacard information is available. Functions #9 and #10 are intended forentities and could be used, for example, by a checkout clerk. Under onearrangement a customer of an entity would place their CardCard into aCardCard data management device 408 to enable the memory of the CardCardto be scanned using Function #9 to find the barcode and/or magneticstripe information corresponding to the data card of the entity.Function #10 would append data card information pertaining to a newentity into the entity database stored on the CardCard. As such, thisfunction could be used, for example, to add a customer to an entity'sloyalty program while the customer is at a POS.

FIG. 9 depicts an exemplary CardCard website in accordance with oneembodiment of the present invention. Referring to FIG. 9, a CardCardwebsite display enables a CardCard Club member, who would typically paya fee to be a member, to select entity types of interest by selecting abutton next to the entity type shown in a first button group 902. Suchentity types, shown as Entity Type A through Entity Type T wouldtypically correspond to categories of entities such as grocery stores,flower shops, gas stations, auto repair, tire, auto dealerships, officesupply, furniture stores, home improvement stores, etc. The displaylists the entities having data cards for the selected entity types wherebuttons from a second group of buttons 904 can be selected to identifyspecific entities for which data card information can be automaticallydownloaded. Typically, such information would be downloaded to aCardCard Club member's computer system 300 and then to the member'sCardCard via a CardCard data management device 408 and a CardCard DataManagement System or similar utility program. The CardCard websiteprovides an easy to use interface for accessing data card informationcorresponding to a large number of entities, which can be categorized invarious ways (e.g., small business, environment friendly, etc.) in orderto tailor the entities listed to the member's tastes and desires.Because of its utility, entities can be charged a premium to advertiseon the site in an attempt to convince the member to select them. Asshown, the website might have one or more sponsors that are always shownor perhaps shown at different times or to users living in certainregions. Logos or advertisements by entities of the selected entitytypes of interest can be displayed. Generally, any of many well knownmethods used to sell advertisement/marketing space on a website can beemployed in accordance with the present invention.

FIG. 10 a depicts an exemplary magnetic stripe 1000 that can be used toidentify an entity, for example, a store from which a CardCard user hasreceived a data card.

FIG. 10 b depicts an exemplary barcode 1002 that can be used to identifyan entity, for example, a store from which a CardCard user has receiveda data card.

FIG. 10 c depicts atop down view of an exemplary entity identifyingdevice 1004 having a magnetic stripe 1000 along one side of a slot asindicated by a thicker line. As shown, a CardCard 104 can be passedthrough the slot of the entity identifying device 1004 and the magneticstripe reader 616 of the CardCard 104 can be used to read the magneticstripe information corresponding to the entity to thereby identify theentity.

FIG. 10 d depicts a top down view of an exemplary entity identifyingdevice 1004 having a barcode 1002 along the bottom of a slot. As shown,CardCard 104 can be passed through the slot of the entity identifyingdevice 1004 and the barcode reader mode of barcode reader/emulator—lighttransceiver 520 or of barcode reader 500 or 516 of the CardCard 104 canbe used to read the barcode information corresponding to the entity tothereby identify the entity.

FIG. 10 e depicts a top down view of an exemplary entity identifyingdevice 1004 having a magnetic stripe along one side of a slot and abarcode along the bottom of the slot. As shown, a CardCard 104 can bepassed through the slot of the entity identifying device 1004 and thebarcode reader/emulator—light transceiver 520 and the magnetic stripereader 616 of the CardCard 104 can be used to read the barcodeinformation and the magnetic stripe information corresponding to theentity to thereby identify the entity.

FIG. 10 f depicts a first three dimensional view of an exemplary entityidentifying device.

FIG. 10 g depicts a second three dimensional view of an exemplary entityidentifying device.

FIG. 11 depicts an exemplary usage of a CardCard at an entitypoint-of-sale 1100.

Referring to FIG. 11, the point-of-sale 1100 includes a point-of-saleterminal 1102, a credit card reader 1104, a register counter 1106, and ahorizontal scanner 308 c. In accordance with the present invention acustomer having information pertaining to the entity's data card loadedinto his or her CardCard 104 can pass the card over magnetic stripe 1000or barcode 1002, or can pass the card through an entity identifyingdevice 1004 associated with the point-of-sale 1100 to identify theentity to the CardCard. Thereafter, the CardCard would configure itselfto output the magnetic stripe and/or barcode information when placedinto credit card reader 1104. If the customer has not previouslypopulated the entity's information into the CardCard, then a CardCarddata management device 408 can be used at the POS 1100 to add theentity's information to the CardCard. A CardCard data management device408, or similar device, can also be used as shown, or as mounted where acustomer can access it, to use the CardCard for two-way transactions,where the CardCard functions as a smart card. If two-way communicationsare employed, the identity of the entity can be conveyed as part of thecommunications thereby eliminating the requirement for the user toidentify the entity as described above. A CardCard data managementdevice 408, or similar device, can also be used to scan the memory of aCardCard to search for data card information corresponding to an entitydata card.

FIG. 12 depicts an exemplary second method corresponding to usage of aCardCard at an entity point-of-sale as depicted in FIG. 11. Referring toFIG. 12, the second method 1200 is the same as the first method 200except the third step 206 of distinguishing an entity of the firstmethod 200 is more specifically defined in the third step 1202 of thesecond method 1200, as using the portable conveyance device to read amagnetic stripe and/or barcode that identifies an entity of theplurality of entities for which the stored magnetic stripe and/orbarcode information of the data card of the entity is required (for thePOS). Thus, as shown in FIG. 11, a customer having a CardCard at anentity's POS (e.g., a grocery store checkout register) could use theCardCard's magnetic stripe and/or barcode reader capabilities to read amagnetic stripe and/or barcode to identify the entity. Thereafter, theCardCard would output the appropriate magnetic stripe and/or barcodeinformation corresponding to the data card of the entity. As such, froma customer's perspective, it would be very simple and intuitive to swipethe CardCard through an entity identifying device 1004 prior to usingthe CardCard with the data card reader of the entity. Depending on whichof the possible configurations for the CardCard and/or a data cardreader that is employed, any of various modes for identifying the entityprior to conveying the appropriate magnetic stripe and/or barcodeinformation corresponding to the data card of the entity can be used inaccordance with the invention including swiping the CardCard through oneor more devices, touching the CardCard to one or more devices, and/orinserting the CardCard into one or more devices, and variouscombinations thereof. Ideally, a CardCard would only have to beinserted, touched, or placed into a single device, for example oneconfigured similar to a CardCard data management device 408, to identifythe entity and output the appropriate information. But, this approachwould require the modification of existing POS infrastructure to includesuch a device. Because such modifications occur over time, it is verylikely that a version of the CardCard will at some point be configuredto work with existing infrastructure and with a single device.

FIG. 13 a depicts an exemplary CardCard display. Referring to FIG. 13 a,a CardCard 104 has on one side a touch screen display 1300. The touchscreen display 1300 has a first group of icons 1302 used to identify anentity type of interest (or category). A first Right Arrow 1304 and afirst Left Arrow 1306 are used to cause the first group of icons 1302displayed above to shift right or left. A user can at any time select anicon by pressing it thereby selecting an entity type of interest wheretypically the selected icon could somehow be identified (e.g., by adifferent brightness level, color, thicker border, etc.). Based on theselected entity type of interest, the entities populated in the CardCardthat correspond to the selected entity type would be displayed in asecond group of icons 1308 used to identify the entity for which theCardCard should output the magnetic stripe and/or barcode informationcorresponding to the data card of the selected entity. A second RightArrow 1310 and a second Left Arrow 1312 are used to cause the secondgroup of icons 1308 displayed above to shift right or left. A user canat any time select an icon by pressing it thereby selecting an entitywhere typically the selected icon could somehow be identified (e.g., bya different brightness level, color, thicker border, etc.). Thereafter,the CardCard 104 would output the magnetic stripe and/or barcodeinformation corresponding to the data card of the selected entity. Itshould be noted that in FIG. 13 a the CardCard is oriented in what iscommonly referred to as a portrait orientation (instead of landscapeorientation). The CardCard could alternatively be oriented in alandscape orientation and could be configured to recognize how it isbeing held by a user to change the orientation of the display fromportrait to landscape and vice versa.

FIG. 13 b depicts a second exemplary CardCard display. Referring to FIG.13 b, a second display 1320 is shown on one side of CardCard 104. Thesecond display 1320 includes a logo display area 1322 where a logo ofthe selected entity is displayed to identify the entity. The seconddisplay 1320 also includes a barcode display area 1324 used to display abarcode corresponding to the data card of the entity such that it can beread by a barcode reading device. It should be noted that in FIG. 13 bthe CardCard is oriented in what is commonly referred to as a landscapeorientation. The CardCard could alternatively be oriented in a portraitorientation and could be configured to recognize how it is being held bya user to change the orientation of the display from portrait tolandscape and vice versa.

Although not required, the CardCard 104 could have substantially thesame shape (i.e., length, width, and thickness) of a conventional creditcard so it could be swiped through a conventional card reader and couldfit in a wallet storage slot as would a conventional credit card.However, the CardCard does not necessarily have to resemble a creditcard or a data card. The portable conveyance device of the presentinvention may alternatively be a cellular phone, a smart phone, a PDA, awatch, a keychain, or any other portable device incorporating circuitrycomparable to the exemplary CardCard circuitry previously described.Such devices may utilize a non-battery power source that can be usedinstead of a battery 606 and may have various controls that can be usedinstead of pressure switches 608 and 610. Such devices may or may notinclude a component that can be inserted into a slot reader. Forexample, an Apple IPhone could be modified to include appropriateCardCard circuitry and have a display interface to select an entitysimilar to what was described in relation to FIG. 13 a (except thearrows would not be required since the IPhone interface allows a user touse a left or right swipe to vary the icons displayed).

FIG. 14 depicts examples of various types of devices that could employCardCard circuitry to enable them to provide CardCard functionality suchas described above.

In an alternative embodiment of the invention, the CardCard would beconfigured to receive a RF transmission, for example, a RFIDtransmission that identifies an entity, for example, the store in whichthe CardCard is located, causing it to display the logo and barcodecorresponding to that entity (as with FIG. 13 b).

In still another embodiment of the invention, the CardCard would have avoice recognition capability allowing the user to provide a voicecommand to identify the entity causing it to display the logo andbarcode corresponding to that entity.

In yet another embodiment of the invention an entity of interest is notidentified in which case when activated the CardCard would repeat thesequence of all barcodes (or subset of barcodes determined via aninterface) on the CardCard and the entity would recognize the barcodethat corresponds to the entity.

While particular embodiments of the invention have been described, itwill be understood, however, that the invention is not limited thereto,since modifications may be made by those skilled in the art,particularly in light of the foregoing teachings.

We claim:
 1. A phone, comprising: a memory for storing a plurality ofdata card information of a plurality of data cards corresponding to aplurality of entities, each data card information of said plurality ofdata card information including a data card barcode corresponding to adata card of said plurality of data cards; an interface for identifyingan entity of said plurality of entities, said interface comprisingbarcode reader capabilities incorporated into said phone, said barcodereader capabilities enabling said phone to read an entity identifyingbarcode provided at a point-of-sale of said entity; a processor forselecting a data card of said plurality of data cards based upon saidentity identifying barcode read by said phone, said selected data cardcorresponding to said identified entity; and a display for displaying adata card barcode of said selected data card.
 2. The phone of claim 1,wherein said plurality of data cards includes at least one loyalty card.3. The phone of claim 1, wherein said interface comprises a graphicaluser interface.
 4. The phone of claim 3, wherein said graphical userinterface allows a user of said phone to identify a data cardcorresponding to said entity using a swipe motion.
 5. The phone of claim1, wherein said interface comprises a transmission.
 6. The phone ofclaim 5, wherein said transmission is a radio frequency transmission. 7.The phone of claim 1, wherein said interface comprises a voicerecognition system.
 8. The phone of claim 1, wherein said phone is acellular phone.
 9. The phone of claim 1, wherein said phone is a smartphone.
 10. The phone of claim 1, wherein said display is configured todisplay a logo corresponding to said identified entity.
 11. The phone ofclaim 1, wherein said plurality of data cards includes at least onecredit card.
 12. The phone of claim 1, wherein said plurality of datacards includes at least one debit card.
 13. The phone of claim 1,wherein said plurality of data cards includes at least oneidentification card.
 14. The phone of claim 1, further comprising: anentity identifying device for providing said entity identifying barcodethat identifies said entity at said point-of-sale of said entity. 15.The phone of claim 1, wherein said interface comprises a magnetic stripereader that reads a magnetic stripe that identifies said entity.
 16. Thephone of claim 1, wherein said interface comprises a transceiver. 17.The phone of claim 16, wherein said transceiver comprises a pulsed lighttransceiver.
 18. The phone of claim 17, wherein said pulsed lighttransceiver uses On-Off-Keying.
 19. The phone of claim 17, wherein saidpulsed light transceiver comprises a light emitting diode.
 20. The phoneof claim 17, wherein said pulsed light transceiver comprises a lightdetector.